Software Requirements Specification

IEEE Software Document Definitions
SQAP – Software Quality Assurance Plan IEEE 730
SCMP – Software Configuration Management Plan IEEE 828
STD – Software Test Documentation IEEE 829
SRS – Software Requirements Specification IEEE 830
SVVP – Software Validation & Verification Plan IEEE 1012
SDD – Software Design Description IEEE 1016
SPMP – Software Project Management Plan IEEE 1058

A Software Requirements Specification ('SRS) – a requirements specification for a software system – is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

Software Requirements is a sub-field of Software engineering that deals with the elicitation, analysis, specification, and validation of requirements for software.[1]

The software requirement specification (SRS) document enlists all necessary requirements for project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with project team and the customer. A general organization of an SRS is as follows [2]

See also

References

  1. ^ Pierre Bourque and Robert Dupuis, ed (2004). Guide to the Software Engineering Body of Knowledge - 2004 Version. IEEE Computer Society. pp. 2–1. ISBN 0-7695-2330-7. http://www.swebok.org. 
  2. ^ Stellman, Andrew and Greene, Jennifer (2005). Applied software project management. O'Reilly Media, Inc. pp. 308. ISBN 0596009488. 

External links